I've found in the docs that the new trace()-function from POV-Ray3.5
only
checks for an intersection with a declared object.

Now I'm wondering. This, if I want to check for an intersection in a
complex
scene, requires me to declare the entire scene, and thus, also to place
it using
object{}.
So, how much does this affect memory consumption?

And, while we're at it:
If I want to do an algorithm that trace()s a plane and places sphere on
top,
and does so over and over again, but is also supposed to place spheres
ON spheres just placed as well...
Do I have to create an array, in which I save the objects placed, and
call on these
again and again for each new sphere?

So, my main question is:
Is there an easy solution which provides me with a way to use trace() on
a
scene, alter it, and use trace() again after the alterations, without
having to
tamper around with arrays and declarations of objects en mass?

Tim

Post a reply to this message